Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

IPv6 (Mulitprotocol support) #41

Closed
wants to merge 6 commits into from
Closed

IPv6 (Mulitprotocol support) #41

wants to merge 6 commits into from

Conversation

cmoeller-dx
Copy link

@cmoeller-dx cmoeller-dx commented Aug 11, 2020 •
edited
Loading

This PR gives the parser the ability to read data from IPv6 speaking clients.
It also provides the capabilty for interpeting multiprotocol submessage types (REACH_NLRI and UNREACH_NLRI).
The new code supports ipv6 and ipv4 in (UN-)REACH messages.

The human readable output will look like this:

[BGPMessage UPDATE] - XXX Bytes
|- MAC: 40:a6:b7:03:d1:28 -> 2c:21:72:af:87:c9
|- IP: [1:7f8:0:0:0:5:4242:c09d]:179 -> [1337:7f8:0:200:0:9:0:1]:59380
|- Timestamp: 2020-08-03 18:49:02.753615 (1596480542.753615)
|
|- Update Message Sub-Type: NONE
|- Withdrawn Routes Length: 0 Bytes
|- Total Path Attribute Length: 107 Bytes
|- Path Attributes: 
|--- ORIGIN: IGP
|--- AS_PATH: 1337
|--- MP_REACH_NLRI:
|----- Next Hop:
|----- 1337:4242:0:0:0:925c:0:1
|----- 1337:1212:0:0:911:b33f:7712:67f2
|----- 
|----- NLRI:
|----- 1337:7331::/32

Filtering for MP_(UN)REACH_NLRI messages are currently not supported.

@cmoeller-dx
Copy link
Author

cmoeller-dx commented Aug 11, 2020 •
edited
Loading

merged with private master. changes can be found in PR #42

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@cmoeller-dx